OTA-2606: rename-provisioning

Fixing stray instance of old terminology

Signed-off-by: Merlin Carter <[email protected]>

docs/enable-implicit-provisioning.adoc

@@ -38,13 +38,13 @@ aktualizr-cert-provider -c credentials.zip -t <device> -d /var/sota/import -r -u
 +
 You can find the link:../src/cert_provider[`aktualizr-cert-provider` source] in this repo. You can also find a compiled binary in the host work directory of bitbake. The path is something like `tmp/work/x86_64-linux/aktualizr-native/1.0+gitAUTOINC+<version>/build/src/cert_provider/aktualizr-cert-provider`.
 
-== Use a Hardware Security Module (HSM) to Provision with Device Credentials
+== Use a Hardware Security Module (HSM) When Provisioning with Device Credentials
 
 As described in the link:prod-intro.html[introduction], it's a good idea to use a Hardware Security Model (HSM) to hold potentially sensitive device credentials.
 
 The following procedure describes how to use QEMU and link:https://www.opendnssec.org/softhsm/[SoftHSM] to simulate a device with an HSM. However, the procedure for your HSM will probably be different. We've provided these instructions as a basic guide to how this provisioning method works but you'll need to make further changes on your own. For example, you'll probably need to adapt your BSP so that aktualizr can access the keys from your HSM.
 
-To enable implicit provisioning with an HSM, follow these steps: ::
+To use an HSM when provisioning with device credentials, follow these steps: ::
 . link:generate-and-install-a-root-certificate.html[Generate and install a root certificate].
 . Add the following lines to your `conf/local.conf`:
 +