anchor.diff:  
       aktualizr -c .
   
  -This will start aktualizr in its normal mode: it will provision with the server using the `credentials.zip` provided, then start listening for updates. You can also xref:aktualizr-runningmodes-finegrained-commandline-control.adoc[selectively trigger aktualizr] or use any of the other options; you just need to specify `-c .` each time.
  +This will start aktualizr in its normal mode: it will provision with the server using the `credentials.zip` provided, then start listening for updates. You can also xref:ota-client::aktualizr-runningmodes-finegrained-commandline-control.adoc[selectively trigger aktualizr] or use any of the other options; you just need to specify `-c .` each time.
   
   You should now be able to see your simulated device provisioned into your OTA Connect account, with two secondary ECUs listed.
   
  
positive.code: 
  * credentials.zip
  * sota_local.toml -- a config file for aktualizr
  * (Optional) A `virtualsec.json` file containing the configuration for one or more secondary ECUs.footnote:[The terms "primary" and "secondary" ECU are used in the Uptane specification. For more information about the difference between primary and secondary ECUs, see our overview of the xref:uptane.adoc#_primary_and_secondary_ecus[Uptane framework\].]
  
  An example directory is below:
  
  
negative.code: == Prerequisites
  
  * A Linux or MacOS machine to run aktualizr on
  * xref:ota-client::generating-provisioning-credentials.adoc[Provisioning credentials] (`credentials.zip` file)
  
  == Install aktualizr locally
  
  