anchor.diff:  NOTE:   The `config/scripts` directory is scanned periodically for changes. New
           and changed templates and scripts are reloaded and deleted templates and
           scripts are removed from the preloaded scripts cache. For more information,
  -        see {ref}/modules-scripting-using.html#reload-scripts[Automatic Script 
  +        see {ref}/modules-scripting-using.html#reload-scripts[Automatic Script
           Reloading] in the Elasticsearch Reference.
   
   To reference a file-based stored or script, you use the formal object definition
  
positive.code: engines use a separate thread pool from the one used to execute watches.
  
  When a watch is triggered, {watcher} queues it up for execution. A `watch_record`
  document is created and added to the watch history and the watch's status is set 
  to `awaits_execution`.
  
  When execution starts, {watcher} creates a watch execution context for the watch.
  The execution context provides scripts and templates with access to the watch 
  metadata, payload, watch ID, execution time, and trigger information. For more 
  information, see <<watch-execution-context, Watch Execution Context>>.
  
  During the execution process, {watcher}:
  
negative.code: [[stored-templates-scripts]]
  ===== Stored Templates and Scripts
  
  If you {ref}/modules-scripting-using.html#modules-scripting-stored-scripts[store]
  your templates and scripts, you can reference them by id.
  
  To reference a stored script or template, you use the formal object definition
  