WIP

src/content/docs/infrastructure/amazon-integrations/connect/Set up auto-discovery of AWS entities.mdx

@@ -19,30 +19,30 @@ With Auto-discovery, you can:
 * Automatically detect and visualize the relationships between AWS entities on the maps.
 * Keep your infrastructure topology updated as changes occur in your AWS environment.
 
-## Set up AWS integration with auto-discovery for your account [setup-auto-discovery-new-integration]
+## Set up AWS integration with auto-discovery for your account
 
 <Steps>
 <Step>
-### Before you begin [auto-discovery-pre-requisites]
+### Before you begin
 To set up AWS integration, ensure you have the following:
 * A New Relic [license key](https://one.newrelic.com/api-keys).
 * An AWS account with [permissions](https://docs.aws.amazon.com/ARG/latest/userguide/gettingstarted-prereqs-permissions.html) to deploy new AWS resources and [IAM roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html).
 * A New Relic account with [permissions](/docs/accounts/accounts-billing/new-relic-one-user-management/user-permissions/#infrastructure) for cloud integrations.
 </Step>
 <Step>
-### Select data type[select-data-type]
+### Select data type
 
 1. Log in to your [New Relic](https://one.newrelic.com/) account and navigate to <DNT>**Infrastructure > AWS**</DNT>.
 3. To integrate with AWS, select a New Relic account and continue.
 4. Select the data type as <DNT>**Metrics**</DNT>, <DNT>**Logs**</DNT>, or both, and continue.
 5. Select <DNT>**Automate AWS with CloudFormation**</DNT> and continue. This is currently the only setup method available for log integration.
 </Step>
 <Step>
-### Select integration method[select-integration-method]
+### Select integration method
 Automating AWS integration with CloudFormation template is the recommended and the only integration method to enable auto-discovery. This method uses a single CloudFormation template to set up your AWS integration and forward New Relic AWS services metrics, logs, or both. Continue with <DNT>**Automate AWS with CloudFormation (Recommended)**</DNT> .
 </Step>
 <Step>
-### Select integration type[select-integration-type]
+### Select integration type
 
 <CollapserGroup>
 <Collapser id="metrics-data-type" title="For Metrics data type">
@@ -81,18 +81,18 @@ Automating AWS integration with CloudFormation template is the recommended and t
 
 </Step>
 <Step>
-### Enable auto-discovery[enable-auto-discovery]
+### Enable auto-discovery
 Turn on the scan to enable auto-discovery of your AWS entities and continue. It enables the `cloudformation:StartResourceScan` permission in your AWS account to scan your AWS resources and discover the relationships between them.
 </Step>
 <Step>
-### Connect to AWS[connect-to-aws]
+### Connect to AWS
 1. Click <DNT>**Launch your CloudFormation in AWS**</DNT> to navigate to your AWS Console. The CloudFormation stack includes the configured parameters based on your selections in New Relic One, so no additional editing is necessary unless you want to make changes.
 2. Copy and paste your license key into your AWS console.
 
 We recommend you store your New Relic license key in <DNT>**[AWS Secrets Manager](https://docs.aws.amazon.com/secretsmanager/latest/userguide/intro.html)**</DNT> by keeping the environment variable set to `true` (default value).
 </Step>
 <Step>
-### Deploy the CloudFormation stack[deploy-cloudformation-stack]
+### Deploy the CloudFormation stack
 After you customize the CloudFormation stack parameters to meet your requirements, click <DNT>**Create stack**</DNT>.
 Creating the stack's resources may take several minutes and may generate multiple stacks, depending on how you configure log and metric forwarding. With a single deployment command, you can create a new stack to forward logs from multiple AWS resources.
 If stack creation fails, refer to the [troubleshooting procedure](/docs/logs/troubleshooting/aws-log-integration-issues/stack-creation-fails).