Update about-keys.md

Author: Ije-oyibo

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

@@ -40,7 +40,7 @@ The base JWK/JWA specifications are also extended to enable key types unique to
 
 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).
+- 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. All new keys and key versions are now created using platform 2 (except UK geo). 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.
 
 These keys are protected in single-tenant HSM-pools. You can import an RSA, EC, and symmetric key, in soft form or by exporting from a supported HSM device. You can also generate keys in HSM pools. When you import HSM keys using the method described in the [BYOK (bring your own key) specification](../keys/byok-specification.md), it enables secure transportation key material into Managed HSM pools.