anchor.diff:  registered with the appropriate trigger engine, and executed according
   to its configured trigger.
   
  -You can also set a watch to the _inactive_ state. Inactive watches are not 
  +You can also set a watch to the _inactive_ state. Inactive watches are not
   registered with a trigger engine and can never be triggered.
   
  -To set a watch to the inactive state when you create it, set the 
  -<<watcher-api-put-watch-active-state, `active`>> parameter to _inactive_. 
  +To set a watch to the inactive state when you create it, set the
  +<<watcher-api-put-watch-active-state, `active`>> parameter to _inactive_.
   To deactivate an existing watch, use the <<watcher-api-deactivate-watch, D
  -eactivate Watch API>>. To reactivate an inactive watch, use the 
  +eactivate Watch API>>. To reactivate an inactive watch, use the
   <<watcher-api-activate-watch, Activate Watch API>>.
   
   NOTE:   You can use the <<watcher-api-execute-watch, Execute Watch API>> to
  
positive.code: {watcher} uses the Elasticsearch script infrastructure, which supports
  <<inline-templates-scripts,inline>>, <<stored-templates-scripts, stored>>, and
  <<file-templates-scripts, file-based scripts>>. Scripts and templates are compiled
  and cached by Elasticsearch to optimize recurring execution.
  {ref}/modules-scripting-using.html#reload-scripts[Autoloading] is also
  supported. For more information, see {ref}/modules-scripting.html[Scripting]
  in the Elasticsearch Reference.
  
  [float]
  [[watch-execution-context]]
  
negative.code: 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
          Reloading] in the Elasticsearch Reference.
  
  To reference a file-based stored or script, you use the formal object definition
  