Updates

Author: msmbaldwin

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

@@ -8,15 +8,15 @@ tags: azure-resource-manager
 ms.service: key-vault
 ms.subservice: certificates
 ms.topic: overview
-ms.date: 09/04/2019
+ms.date: 01/04/2023
 ms.author: mbaldwin
 ---
 
 # About Azure Key Vault certificates
 
 Azure Key Vault certificate support provides for management of your X.509 certificates and the following behaviors:  
 
-- Allows a certificate owner to create a certificate through a key vault creation process or through the import of an existing certificate. This includes both self-signed certificates and certificates that are generated from a certificate authority (CA).
+- Allows a certificate owner to create a certificate through a key vault creation process or through the import of an existing certificate. Imported certificates include both self-signed certificates and certificates that are generated from a certificate authority (CA).
 - Allows a Key Vault certificate owner to implement secure storage and management of X.509 certificates without interacting with private key material.  
 - Allows a certificate owner to create a policy that directs Key Vault to manage the lifecycle of a certificate.  
 - Allows a certificate owner to provide contact information for notifications about the lifecycle events of expiration and renewal.  
@@ -66,7 +66,7 @@ A Key Vault certificate has the following attribute:
 
 - `enabled`: This Boolean attribute is optional. Default is `true`. It can be specified to indicate if the certificate data can be retrieved as a secret or operable as a key. 
 
-  This attribute is also used in conjunction with `nbf` and `exp` when an operation occurs between `nbf` and `exp`, but only if `enabled` is set to `true`. Operations outside the `nbf` and `exp` window are automatically disallowed.  
+  This attribute is also used with `nbf` and `exp` when an operation occurs between `nbf` and `exp`, but only if `enabled` is set to `true`. Operations outside the `nbf` and `exp` window are automatically disallowed.  
 
 A response includes these additional read-only attributes:
 
@@ -96,7 +96,7 @@ At a high level, a certificate policy contains the following information:
 - X.509 certificate properties, which include subject name, subject alternate names, and other properties that are used to create an X.509 certificate request.  
 - Key properties, which include key type, key length, exportable, and `ReuseKeyOnRenewal` fields. These fields instruct Key Vault on how to generate a key. 
 
-  [Supported key types](/rest/api/keyvault/certificates/create-certificate/create-certificate#jsonwebkeytype) are RSA, RSA-HSM, EC, EC-HSM, and oct. 
+  [Supported key types](/rest/api/keyvault/certificates/create-certificate/create-certificate#jsonwebkeytype) are RSA, RSA-HSM, EC, EC-HSM, and oct.
 - Secret properties, such as the content type of an addressable secret to generate the secret value, for retrieving a certificate as a secret.  
 - Lifetime actions for the Key Vault certificate. Each lifetime action contains:  
 

articles/key-vault/certificates/index.yml

@@ -12,7 +12,7 @@ metadata:
   ms.topic: landing-page # Required
   author: msmbaldwin
   ms.author: mbaldwin
-  ms.date: 04/07/2020 #Required; mm/dd/yyyy format.
+  ms.date: 01/04/2023
 
 # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
 

articles/key-vault/certificates/quick-create-node.md

@@ -3,7 +3,7 @@ title: Quickstart -  Azure Key Vault certificate client library for JavaScript (
 description: Learn how to create, retrieve, and delete certificates from an Azure key vault using the JavaScript client library
 author: msmbaldwin
 ms.author: mbaldwin
-ms.date: 12/13/2021
+ms.date: 01/04/2023
 ms.service: key-vault
 ms.subservice: certificates
 ms.topic: quickstart
@@ -33,7 +33,7 @@ For more information about Key Vault and certificates, see:
     - [Azure portal](../general/quick-create-portal.md) 
     - [Azure PowerShell](../general/quick-create-powershell.md)
 
-This quickstart assumes you are running [Azure CLI](/cli/azure/install-azure-cli).
+This quickstart assumes you're running [Azure CLI](/cli/azure/install-azure-cli).
 
 ## Sign in to Azure
 
@@ -111,7 +111,7 @@ export KEY_VAULT_NAME=<your-key-vault-name>
 
 ## Code example
 
-The code samples below will show you how to create a client, set a certificate, retrieve a certificate, and delete a certificate. 
+These code samples demonstrate how to create a client, set a certificate, retrieve a certificate, and delete a certificate. 
 
 ### Set up the app framework
 
@@ -233,11 +233,11 @@ The code samples below will show you how to create a client, set a certificate,
 
 ## Integrating with App Configuration
 
-The Azure SDK provides a helper method, [parseKeyVaultCertificateIdentifier](/javascript/api/@azure/keyvault-certificates#parseKeyVaultCertificateIdentifier_string_), to parse the given Key Vault certificate ID. This is necessary if you use [App Configuration](../../azure-app-configuration/index.yml) references to Key Vault. App Config stores the Key Vault certificate ID. You need the _parseKeyVaultCertificateIdentifier_ method to parse that ID to get the certificate name. Once you have the certificate name, you can get the current certificate using code from this quickstart. 
+The Azure SDK provides a helper method, [parseKeyVaultCertificateIdentifier](/javascript/api/@azure/keyvault-certificates#parseKeyVaultCertificateIdentifier_string_), to parse the given Key Vault certificate ID, which is necessary if you use [App Configuration](../../azure-app-configuration/index.yml) references to Key Vault. App Config stores the Key Vault certificate ID. You need the _parseKeyVaultCertificateIdentifier_ method to parse that ID to get the certificate name. Once you have the certificate name, you can get the current certificate using code from this quickstart. 
 
 ## Next steps
 
-In this quickstart, you created a key vault, stored a certificate, and retrieved that certificate. To learn more about Key Vault and how to integrate it with your applications, continue on to the articles below.
+In this quickstart, you created a key vault, stored a certificate, and retrieved that certificate. To learn more about Key Vault and how to integrate it with your applications, continue on to these articles.
 
 - Read an [Overview of Azure Key Vault](../general/overview.md)
 - Read an [Overview of certificates](about-certificates.md)