diff --git a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking.mdx b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking.mdx
index 68938c646e3..14c6d12189d 100644
--- a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking.mdx
+++ b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking.mdx
@@ -8,9 +8,10 @@ redirects:
 
 This is the first step to [enable New Relic's AWS Lambda monitoring](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/enable-aws-lambda-monitoring).
 
-When you link your AWS account to New Relic, you're granting permission to New Relic to create an inventory of your AWS account, and gather CloudWatch metrics for your Lambda functions. Resources in your AWS account then show up as entities in the [explorer](/docs/new-relic-one/use-new-relic-one/ui-data/new-relic-one-entity-explorer-view-performance-across-apps-services-hosts), decorated with config information.
+When you link your AWS account to New Relic, you're granting permission to New Relic to create an inventory of your AWS account, and gather CloudWatch metrics for your Lambda functions. Resources in your AWS account then show up as entities in [New Relic Explorer](/docs/new-relic-one/use-new-relic-one/ui-data/new-relic-one-entity-explorer-view-performance-across-apps-services-hosts), decorated with config information.
+
+For Lambda serverless function monitoring to work, it requires either an [API Polling](/docs/infrastructure/amazon-integrations/connect/connect-aws-new-relic-infrastructure-monitoring) or [Metric Streams](/docs/infrastructure/amazon-integrations/connect/aws-metric-stream) integration. You can set up your choice of integration before you start this account linking, or you can let the CLI install the API Polling integration for you.
 
-For Lambda serverless function monitoring to work, it requires either  an [API Polling](/docs/infrastructure/amazon-integrations/connect/connect-aws-new-relic-infrastructure-monitoring) or [Metric Streams](/docs/infrastructure/amazon-integrations/connect/aws-metric-stream) integration. You can set up your choice of integration before you start this account linking, or you can let the CLI install the API Polling integration for you.
 
 <CollapserGroup>
   <Collapser
@@ -51,12 +52,13 @@ To enable serverless monitoring using our Lambda layer, you need the following:
 
 * [AWS CLI v2](https://docs.aws.amazon.com/cli/latest/userguide/install-cliv2.html) installed and configured using `aws configure`.
 * [Python](https://www.python.org/downloads/) version 3.3 or higher installed.
-* [newrelic-lambda CLI](https://github.com/newrelic/newrelic-lambda-cli#installation),
-  which you can install by running `pip3 install newrelic-lambda-cli`.
+* [newrelic-lambda CLI](https://github.com/newrelic/newrelic-lambda-cli#installation), which you can install by running `pip3 install newrelic-lambda-cli`.
 * A New Relic account. You must have an admin role or have the **Infrastructure manager** [add-on role](/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model#add-on).
 * A <InlinePopover type="userKey" />.
 * An AWS account with permissions for creating IAM resources, managed secrets, and Lambdas. You also need permissions for creating CloudFormation stacks and S3 buckets.
 
+For in-depth detail about the CLI, see [our CLI repo](https://github.com/newrelic/newrelic-lambda-cli#installation).
+
 <CollapserGroup>
   <Collapser
     id="cli-aws-permissions"
@@ -322,6 +324,16 @@ The `newrelic-lambda` CLI adds your New Relic <InlinePopover type="licenseKey" /
 
 ## Troubleshooting [#troubleshooting]
 
+For a series of troubleshooting guides for Lambda, see these posts on our Support Forum: 
+
+* [General knowledge Part 1](https://forum.newrelic.com/s/hubtopic/aAX8W0000008bkgWAA/lambda-troubleshooting-framework-general-knowledge-part-1)
+* [General knowledge Part 2](https://forum.newrelic.com/s/hubtopic/aAX8W0000008brSWAQ/lambda-troubleshooting-framework-general-knowledge-part-2)
+* [Install details by method](https://forum.newrelic.com/s/hubtopic/aAX8W0000008bkhWAA/lambda-troubleshooting-framework-installation-details-by-method)
+* [Troubleshooting Lambda Part 1](https://forum.newrelic.com/s/hubtopic/aAX8W0000008eWvWAI/lambda-troubleshooting-framework-troubleshooting-lambda-part-1)
+* [Troubleshooting Lambda Part 2](https://forum.newrelic.com/s/hubtopic/aAX8W0000008brRWAQ/lambda-troubleshooting-framework-troubleshooting-lambda-part-2)
+
+Here are more details on other problems and solutions. 
+
 ### Cannot use AWS secrets manager [#cannot-use-secrets]
 
 If your organization does not allow the use of AWS Secrets Manager, the New Relic Lambda Extension will accept a `NEW_RELIC_LICENSE_KEY` environment variable. Add the `--disable-license-key-secret` flag from the `newrelic-lambda integrations install` command. Then set this environment variable to your <InlinePopover type="licenseKey" /> in your Lambda function configuration.