diff --git a/docs/Signing.md b/docs/Signing.md
index bd61ffed..8f78520d 100644
--- a/docs/Signing.md
+++ b/docs/Signing.md
@@ -125,7 +125,7 @@ wolfBoot also supports verifying firmware images using certificate chains instea
 
 To generate an image for use with this mode, pass the `--cert-chain CERT_CHAIN.der` option to the sign tool, where `CERT_CHAIN.der` is a der encoded certificate chain containing one or more certificates in SSL order (leaf/signer cert last). Note that the sign tool still expects a signing private key to be provided as described above, and assumes that the public key of the signer cert in the chain corresponds to the signing private key.
 
-Certificate chain verification of images is currently limited to use in conjuction with wolfHSM. See [wolfHSM.md](wolfHSM.md) for more details.
+Certificate chain verification of images is currently limited to use in conjunction with wolfHSM. See [wolfHSM.md](wolfHSM.md) for more details.
 
 #### Target partition id (Multiple partition images, "self-update" feature)
 
diff --git a/hal/sim.c b/hal/sim.c
index a1e3e208..3b4b3f8e 100644
--- a/hal/sim.c
+++ b/hal/sim.c
@@ -101,7 +101,7 @@ const int       hsmClientDevIdCrypt = WH_DEV_ID;
 const int       hsmClientKeyIdCrypt = 0xFF;
 #endif
 #ifdef WOLFBOOT_CERT_CHAIN_VERIFY
-const int       hsmClientNvmIdCertRootCA = 1;
+const whNvmId hsmClientNvmIdCertRootCA = 1;
 #endif
 
 int hal_hsm_init_connect(void);