Update about-keys.md

Author: Ije-oyibo

articles/key-vault/keys/about-keys.md

@@ -38,7 +38,7 @@ Cryptographic keys in Key Vault are represented as JSON Web Key [JWK] objects. T
 
 The base JWK/JWA specifications are also extended to enable key types unique to the Azure Key Vault and Managed HSM implementations. 
 
-HSM-protected keys (also referred to as HSM-keys) are processed in an HSM (Hardware Security Module) and always remain HSM protection boundary. 
+HSM Keys in vaults are protected". The Software keys are not protected by HSMs.
 
 - Keys stored in vaults benefit from robust protection using **FIPS 140-2 HSMs**. There are two distinct HSM platforms available: 1 which protects key versions with**FIPS 140-2 Level 2**  and 2 which protects keys with **FIPS 140-2 Level 3** HSMs depending on when the key was created. To determine which HSM Platform is protecting a key version, get it's [hsmPlatform](about-keys-details.md#key-attributes).
 - Managed HSM  uses **FIPS 140-2 Level 3** validated HSM modules to protect your keys. Each HSM pool is an isolated single-tenant instance with its own [security domain](../managed-hsm/security-domain.md) providing complete cryptographic isolation from all other HSMs sharing the same hardware infrastructure.
@@ -72,7 +72,7 @@ Key Vault supports RSA and EC keys. Managed HSM supports RSA, EC, and symmetric
 
 |Key type and destination|Compliance|
 |---|---|
-|Software-protected keys in vaults (Premium & Standard SKUs) | FIPS 140-2 Level 1|
+|Software-protected (hsmPlatform 0) keys in vaults | FIPS 140-2 Level 1|
 |hsmPlatform 1 protected keys in vaults (Premium SKU)| FIPS 140-2 Level 2|
 |hsmPlatform 2 protected keys in vaults (Premium SKU)| FIPS 140-2 Level 3|
 |Keys in Managed HSM are always HSM protected|FIPS 140-2 Level 3|