anchor.diff:  
   `source`, `id`::
   
  -    The script itself, which you specify as `source` for an inline script or `id` for a stored script. Use the `_scripts` endpoint to retrieve a stored script. For example, you can create or delete a <<script-stored-scripts,stored script>> by calling `POST _scripts/{id}` and `DELETE _scripts/{id}`.
  +    The script itself, which you specify as `source` for an inline script or
  +    `id` for a stored script. Use the <<stored-script-apis,stored script APIs>>
  +    to create and manage stored scripts.
   
   `params`::
   
  
positive.code:   }
  }
  ----
  // TEST[continued]
  <1> `id` of the stored script
  
  To delete a stored script, submit a delete request to the `_scripts` endpoint
  and specify the stored script `id`:
  
  [source,console]
  ----
  
negative.code: [discrete]
  [[script-stored-scripts]]
  === Store and retrieve scripts
  You can store and retrieve scripts from the cluster state using the
  <<stored-script-apis,stored script APIs>>. Stored scripts reduce compilation
  time and make searches faster.
  
  NOTE: Unlike regular scripts, stored scripts require that you specify a script
  language using the `lang` parameter.
  
  To create a script, use the <<create-stored-script-api,create stored script
  API>>. For example, the following request creates a stored script named
  `calculate-score`.
  
  [source,console]
  ----
  POST _scripts/calculate-score
  {
    "script": {
  