anchor.diff:  
   An update cycle consists of:
   
  -. Polling the server for updates and downloading (and verifying) update metadata
  -. Downloading (and verifying) any update binaries available
  -. Installing the update
  -. Reporting the install results
  +. Polling the server for updates and downloading (and verifying) update metadata.
  +. Downloading (and verifying) any update binaries available.
  +. Installing the update.
  +. Reporting the install results.
   
  -To trigger the whole cycle, use
  +To trigger the whole cycle, use the following command:
   
       aktualizr --running-mode=once
   
  
positive.code: 
      aktualizr --running-mode=check
  
  
negative.code: = Selectively triggering aktualizr
  
  Aktualizr normally runs as a `systemd` service and regularly polls for updates. The default polling interval is set at 10s, and this should be increased by a few orders of magnitude in a production system.
  
  It is also possible to trigger the update cycle, or individual parts of the update cycle, manually or programmatically. This is done by using aktualizr's `--running-mode` option (or by setting `running_mode` in the `[uptane]` configuration section).
  
  [NOTE]
  ====
  To selectively trigger aktualizr, you should disable the `systemd` service. If aktualizr runs continuously, it interferes with the manual triggering.
  
  To run the update cycle manually, first stop and disable the aktualizr background service:
  
      systemctl stop aktualizr && systemctl disable aktualizr
  
  Assuming aktualizr is being built using Yocto and meta-updater, the `systemd` service can also be disabled by default by adding the following to `local.conf`:
  
      `systemd`_AUTO_ENABLE_aktualizr = "disable"
  ====
  
  WARNING: This interface may change in the future, possibly to a socket- or dbus-based system.
  