Update azure-policy.md

Author: sebansal

articles/key-vault/general/azure-policy.md

@@ -152,7 +152,7 @@ This policy audits all secrets in your key vault and flags secrets that do not h
 
 If a secret is too close to expiration, an organizational delay to rotate the secret may result in an outage. Secrets should be rotated at a specified number of days prior to expiration to provide sufficient time to react to a failure. This policy will audit secrets that are too close to their expiration date and allows you to set this threshold in days. You can also use this policy to prevent the creation of new secrets that are too close to their expiration date.
 
-### Secrets should have the specified maximum validity period (
+### Secrets should have the specified maximum validity period 
 
 Manage your organizational compliance requirements by specifying the maximum amount of time in days that a secret can be valid within your key vault. Secrets that are valid longer than the threshold you set will be marked as non-compliant. You can also use this policy to block the creation of new secrets that have an expiration date set longer than the maximum validity period you specify.