Updating in progress: Editorial review comments

Author: sujitnewrelic

src/content/docs/apis/nerdgraph/examples/nerdgraph-api-secret-management-service.mdx

@@ -4,18 +4,24 @@ metaDescription: "Learn how to use the Secret Management Service to securely sto
 freshnessValidatedDate: never
 ---
 
-When you're working with New Relic, you might need to store sensitive information like API keys and application credentials. In New Relic, these are called secrets. The <dnt>secrets management</dnt> service provides a secure way to store and retrieve these secrets in a centralized location through our [NerdGraph API](/docs/apis/nerdgraph/get-started/introduction-new-relic-nerdgraph/). You can store secrets only in string format.
+When you're working with New Relic, you might need to store sensitive information like API keys and application credentials. In New Relic, these are called secrets. The <dnt>secrets management</dnt> service provides a secure way to store and retrieve these secrets in a centralized location through our [NerdGraph API](/docs/apis/nerdgraph/get-started/introduction-new-relic-nerdgraph/). 
 
+<Callout variant="important">
+
+You can store secrets only in string format.
+
+</Callout>
 
-The key features of the <dnt>secrets management</dnt> service are as follows:
+The key features of the <dnt>secrets management</dnt> service are:
 
-* **Unique keys for secrets**: You need to assign a unique key to each secret you store. This key is used to identify the secret when you want to retrieve or manage it.
+* **Unique keys for secrets**: You can prevent accidental exposure of secrets by assigning a unique key to each one when storing. Use the key to retrieve and manage the secrets.
 
-* **Secrets at [account or organization level](/docs/accounts/accounts-billing/account-structure/new-relic-account-structure/)**: If a secret must be accessed and used across multiple accounts, you can store it at the organization level. Conversely, if the secret is specific to an account and does not need cross-account access, you can store it at the account level.
+* **Secrets stored  at [account or organization level](/docs/accounts/accounts-billing/account-structure/new-relic-account-structure/)**: 
+To access and use a secret across multiple accounts, you can store it at the organization level. For a secret is specific to a single account, you can store it at the account level.
 
 * **Versions of secrets**: You can update a secret without losing the previous version. The <dnt>secrets management</dnt> service tracks all versions of a secret, allowing you to retrieve up to 10 previous versions.
 
-* **Soft delete and secrets recovery**: You can temporarily delete a secret and recover it later. This is useful if you accidentally delete a secret or need to restore a previous version. You can also purge a secret, which permanently removes it from the system.
+* **Temporary deletion and recovery of secrets**: You can delete a secret temporarily and recover it later, which is useful for restoring previous versions.
 
 * **Access control**: As an admin, you can define who can access the secret by setting custom roles and permissions, and specifying the scope of access. The scope can range from basic read-only access to purge access.
 
@@ -190,7 +196,7 @@ The operations you can perform with the <dnt>secrets management</dnt> service ar
 <CollapserGroup>
   <Collapser 
   id="create-secret" 
-  title="store a secret">
+  title="Store a secret">
 
 Use the `secretsManagementCreateSecret` mutation with the following partameters to store a secret. 
 
@@ -258,7 +264,7 @@ Use the `secretsManagementCreateSecret` mutation with the following partameters
             </td>
             <td>
 
-             * `type`: Based on your permission and need, select `Account` or `Organization`.
+             * `type`: Based on your permissions and requirements, select `Account` or `Organization`.
              * `id`: Enter the corresponding ID of the account or organization.
             </td>
         </tr>
@@ -407,7 +413,7 @@ mutation {
 Use the `secretsManagementUpdateSecret` mutation to update the value of existing secrets.
 
 <Callout variant="tip">
-Each update operation creates a new version of the secret. The highest version is always the latest version of the secret.
+Each update operation creates a new version of the secret. The highest version is always the latest version of the secret. To rertieve older versions of the secret, you can use the `{customerAdministration {secretVersions}}` query. For more details, refer to the [Retrieve all versions of a secret](/#recover-secrets-versions) section.
 </Callout>
 
 #### Input Parameters