anchor.diff:  trigger engine. Typically for the `schedule` trigger, the scheduler is the
   trigger engine.
   
  -IMPORTANT:  Putting a watch must be done via this API only. Do not put a watch
  -            directly to the `.watches` index using the Elasticsearch Index API.
  -            If {es} {security-features} are enabled, make sure no `write`
  -            privileges are granted to anyone over the `.watches` index.
  +IMPORTANT:  You must use {kib} or this API to create a watch. Do not put a watch
  +            directly to the `.watches` index using the Elasticsearch index API.
  +            If {es} {security-features} are enabled, do not give users `write`
  +            privileges on the `.watches` index.
   
   When adding a watch you can also define its initial
  -{xpack-ref}/how-watcher-works.html#watch-active-state[active state]. You do that
  +{stack-ov}/how-watcher-works.html#watch-active-state[active state]. You do that
   by setting the `active` parameter.
   
   [float]
  
positive.code: ==== Authorization
  
  You must have `manage_watcher` cluster privileges to use this API. For more
  information, see {xpack-ref}/security-privileges.html[Security Privileges].
  
  [float]
  ==== Security Integration
  
negative.code: <titleabbrev>Put watch</titleabbrev>
  ++++
  
  The PUT watch API either registers a new watch in {watcher} or updates an
  existing one.
  
  [float]
  