Update correlate secrets docs

Author: jonathanfrappier

content/hcp-docs/content/docs/vault-radar/agent/correlate-aws-secrets-manager.mdx

@@ -6,20 +6,27 @@ description: >-
 
 # Correlate findings with AWS Secrets Manager
 
-When HCP Vault Radar connects to AWS Secrets Manager, Vault Radar can correlate findings with secrets stored in AWS Secrets Manager. This allows you to identify what secrets you need to rotate.
+When HCP Vault Radar connects to AWS Secrets Manager, Vault Radar can correlate
+findings with secrets stored in AWS Secrets Manager. This allows you to identify
+what secrets you need to rotate.
 
 ## Connect AWS Secrets Manager
 
-Before you can correlate findings with AWS Secrets Manager, you need to [deploy the Radar agent](/hcp/docs/vault-radar/agent/deploy). Once you deploy the agent, you can configure and connect AWS Secrets Manager to the agent.
+Before you can correlate findings with AWS Secrets Manager, you need to [deploy
+the Radar agent](/hcp/docs/vault-radar/agent/deploy). Once you deploy the agent,
+you can configure and connect AWS Secrets Manager to the agent.
 
 ## Prerequisites
 
-You need one of the following authentication methods:
+You need one of the following AWS authentication methods:
 
 - IAM role authentication with an EC2 instance or configured IAM role
 - Environment variables authentication with AWS Access Key ID and Secret Access Key
 
-Both authentication methods support an optional assume role ARN for cross-account access or elevated permissions. For more information about assuming roles, refer to the [AWS STS AssumeRole documentation](https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRole.html).
+Both authentication methods support an optional assume role ARN for
+cross-account access or elevated permissions. For more information about
+assuming roles, refer to the [AWS STS AssumeRole
+documentation](https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRole.html).
 
 ### Required permissions
 
@@ -36,37 +43,44 @@ The IAM user, role, or assumed role must have the following permissions:
 
 ## Agent configuration with AWS Secrets Manager
 
-Set up and manage AWS Secrets Manager from the Vault Radar module in the [HCP Portal](https://portal.cloud.hashicorp.com/). Select **Settings**, then **Secret Managers**, and then click **Connect new secret manager**.
+Set up and manage AWS Secrets Manager from the Vault Radar module in the [HCP
+Portal](https://portal.cloud.hashicorp.com/). 
 
-1. Select **AWS Secrets Manager** and click **Next**.
-
-1. Select an AWS authentication method from the **Authentication method** pulldown menu.
-
-1. Enter the details for the selected method and click **Next** to validate the connection.
-
-<Tabs>
-<Tab heading="IAM Role">
-
-Select **IAM Role** if you want to use instance profile or role-based authentication.
+1. Click **Settings**.
 
-![IAM Role](/img/docs/vault-radar/indexing/aws-secrets-manager/iam-role.png)
+1. Click **Secret Managers**.
 
-1. (Optional) Enter an assume role ARN in the **Assume Role ARN** text field if you need to assume a different role for access.
+1. Click **Connect new secret manager**.
 
-</Tab>
-<Tab heading="Environment Variables">
-
-Select **AWS Credentials from environment variables** if you want to use access keys.
-
-![Environment Variables](/img/docs/vault-radar/indexing/aws-secrets-manager/environment-variables.png)
-
-1. Enter your AWS Access Key ID location in the **AWS Access Key ID Env variable** text field (default: `env://AWS_ACCESS_ID_LOCATION`).
-
-1. Enter your AWS Secret Access Key location in the **AWS Secret Access Key Env variable** text field (default: `env://AWS_SECRET_KEY_LOCATION`).
+1. Select **AWS Secrets Manager** and click **Next**.
 
-1. (Optional) Enter an assume role ARN in the **Assume Role ARN** text field if you need to assume a different role for access.
+1. Select an AWS authentication method from the **Authentication method** pulldown menu.
 
-</Tab>
-</Tabs>
+1. Enter the details for the selected method and click **Next** to validate the connection.
 
-1. Vault Radar fetches all active regions for the account and automatically starts index scanning for each region.
+   <Tabs>
+   <Tab heading="IAM Role">
+   
+   - Select **IAM Role** if you want to use instance profile or role-based authentication.
+   
+   ![IAM Role](/img/docs/vault-radar/indexing/aws-secrets-manager/iam-role.png)
+   
+   - (Optional) Enter an assume role ARN in the **Assume Role ARN** text field if you need to assume a different role for access.
+   
+   </Tab>
+   <Tab heading="Environment Variables">
+   
+   - Select **AWS Credentials from environment variables** if you want to use access keys.
+   
+   ![Environment Variables](/img/docs/vault-radar/indexing/aws-secrets-manager/environment-variables.png)
+   
+   - Enter your AWS Access Key ID location in the **AWS Access Key ID Env variable** text field (default: `env://AWS_ACCESS_ID_LOCATION`).
+   
+   - Enter your AWS Secret Access Key location in the **AWS Secret Access Key Env variable** text field (default: `env://AWS_SECRET_KEY_LOCATION`).
+   
+   - (Optional) Enter an assume role ARN in the **Assume Role ARN** text field if you need to assume a different role for access.
+   
+   </Tab>
+   </Tabs>
+
+Vault Radar fetches all active regions for the account and automatically starts index scanning for each region.

content/hcp-docs/content/docs/vault-radar/agent/correlate-vault.mdx

@@ -13,15 +13,26 @@ Vault Dedicated or Vault Enterprise clusters.
 
 </Highlight>
 
-When the HCP Vault Radar agent connects to a HCP Vault Dedicated or Vault Enterprise cluster, 
+When the Vault Radar agent connects to a Vault Dedicated or Vault Enterprise cluster, 
 Vault Radar can correlate findings with secrets stored in Vault. This allows you to identify 
 what secrets you need to rotate.
 
 ## Connect a Vault cluster
 
 Before you can correlate findings with Vault, you need to [deploy the Radar
 agent](/hcp/docs/vault-radar/agent/deploy). Once you deploy the agent, you can
-configured and connect Vault to the agent.
+configure and connect Vault to the agent.
+
+## Prerequisites
+
+You need one of the following Vault authentication methods:
+
+- Kubernetes
+- AppRole
+- Token
+
+The authentication methods requires a policy to all the Vault Radar agent to
+read secrets from Vault.
 
 ### Create a Vault policy