Update platform/core-concepts.mdx

Co-authored-by: Herman Slatman <hslatman@users.noreply.github.com>

Author: tashian

platform/core-concepts.mdx

@@ -41,7 +41,7 @@ A high-assurance device identity requires:
 * Cryptographic binding between the trusted platform and the trusted secure element (provided by the platform)
 * Proof that a private key associated with the device is **hardware-bound** on its secure element. Hardware-bound keys can be used by the device, but there’s no way to extract them without an exploit or destructive disassembly in a semiconductor forensics lab.
 
-Once this identity is established and a device certificate is issued, a third party (aka “relying party”) can trust not only the identity of the device, but the residency of keys generated in its secure element. 
+Once this identity is established and a device certificate is issued, a third party (aka “relying party”) can trust not only the identity of the device, but also verify the residency of keys generated in its secure element. 
 
 Now we have a great foundation for device identity. And, we've unlocked another gift: **Zero-touch provisioning**. It's possible for new devices to automatically enroll themselves on their first boot, with no credentials required.