anchor.diff:  --------------------------------------------------
   // CONSOLE
   
  -The `simple_query_string` top level parameters include:
  -
  -[cols="<,<",options="header",]
  -|=======================================================================
  -|Parameter |Description
  -|`query` |The actual query to be parsed. See below for syntax.
  -
  -|`fields` |The fields to perform the parsed query against. 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.
  -
  -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.
  -
  -|`default_operator` |The default operator used if no explicit operator
  -is specified. For example, with a default operator of `OR`, the query
  -`capital of Hungary` is translated to `capital OR of OR Hungary`, and
  -with default operator of `AND`, the same query is translated to
  -`capital AND of AND Hungary`. The default value is `OR`.
  -
  -|`analyzer` |Force the analyzer to use to analyze each term of the query when
  -creating composite queries.
  -
  -|`flags` |A set of <<supported-flags,flags>> specifying which features of the 
  -`simple_query_string` to enable. Defaults to `ALL`.
  -
  -|`analyze_wildcard` | Whether terms of prefix queries should be automatically
  -analyzed or not. If `true` a best effort will be made to analyze the prefix. However,
  -some analyzers will be not able to provide a meaningful results
  -based just on the prefix of a term. Defaults to `false`.
  -
  -|`lenient` | If set to `true` will cause format based failures
  -(like providing text to a numeric field) to be ignored.
  -
  -|`minimum_should_match` | The minimum number of clauses that must match for a
  - document to be returned. See the
  - <<query-dsl-minimum-should-match,`minimum_should_match`>> documentation for the
  - full list of options.
  -
  -|`quote_field_suffix` | A suffix to append to fields for quoted parts of
  -the query string. This allows to use a field that has a different analysis chain
  -for exact matching. Look <<mixing-exact-search-with-stemming,here>> for a
  -comprehensive example.
  -
  -|`auto_generate_synonyms_phrase_query` |Whether phrase queries should be automatically generated for multi terms synonyms.
  -Defaults to `true`.
  -
  -|`all_fields` |  deprecated[6.0.0, set `fields` to `*` instead]
  -Perform the query on all fields detected in the mapping that can
  -be queried.
  -
  -|`fuzzy_prefix_length` |Set the prefix length for fuzzy queries. Default
  -is `0`.
  -
  -|`fuzzy_max_expansions` |Controls the number of terms fuzzy queries will
  -expand to. Defaults to `50`
  -
  -|`fuzzy_transpositions` |Set to `false` to disable fuzzy transpositions (`ab` -> `ba`).
  -Default is `true`.
  -|=======================================================================
  -
  -[float]
  -===== Simple Query String Syntax
  -The `simple_query_string` supports the following special characters:
  +
  +[[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
  
positive.code: * `~N` after a word signifies edit distance (fuzziness)
  * `~N` after a phrase signifies slop amount
  
  In order to search for any of these special characters, they will need to
  be escaped with `\`.
  
  Be aware that this syntax may have a different behavior depending on the
  `default_operator` value. For example, consider the following query:
  
  [source,js]
  --------------------------------------------------
  
negative.code: --------------------------------------------------
  // CONSOLE
  
  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,js]
  --------------------------------------------------
  