anchor.diff:  // NOTCONSOLE
   
   [[random-score]]
  -===== `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`
   `field_value_factor` function can be easily implemented through script:
   
   [source,js]
  
positive.code: NOTE: Decay functions on dates are limited to dates in the default format
  and default time zone. Also calculations with `now` are not supported.
  
  ===== Functions for vector fields
  <<vector-functions, Functions for vector fields>> are accessible through
  `script_score` query.
  
  ==== Faster alternatives
  Script Score Query calculates the score for every hit (matching document).
  There are faster alternative query types that can efficiently skip
  non-competitive hits:
  
  * If you want to boost documents on some static fields, use
   <<query-dsl-rank-feature-query, Rank Feature Query>>.
  
  
  ==== Transition from Function Score Query
  We are deprecating <<query-dsl-function-score-query, Function Score>>, and
  Script Score Query will be a substitute for it.
  
  Here we describe how Function Score Query's functions can be
  equivalently implemented in Script Score Query:
  
  [[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:
  
  
negative.code: --------------------------------------------------
  // CONSOLE
  
  
  [[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 <<relevance-scores,relevance score>> lower
  than this floating point number are excluded from the search results.
  
  
  [[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]
  