fix(serverless): making changes from peer

newrelic · Apr 30, 2024 · 62b3084 · 62b3084
1 parent b37fc10
commit 62b3084
Show file tree

Hide file tree

Showing 6 changed files with 9 additions and 9 deletions.
diff --git a/...n-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking.mdx b/...n-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Step 1: Link your AWS and New Relic accounts"
+title: "Link your AWS and New Relic accounts"
 metaDescription: Step 1 of enabling New Relic AWS Lambda Monitoring.
 redirects:
   - /docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-serverless-monitoring-using-lambda-layer

diff --git a/...itoring/enable-lambda-monitoring/configure-serverless-monitoring-aws-lambda.mdx b/...itoring/enable-lambda-monitoring/configure-serverless-monitoring-aws-lambda.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Step 5: Additional configuration"
+title: "Additional configuration"
 metaDescription: After enabling New Relic's AWS Lambda monitoring, you can set up alerts and custom events.
 redirects:
   - /docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/configure-new-relic-serverless-aws-lambda

diff --git a/...itoring/aws-lambda-monitoring/enable-lambda-monitoring/containerized-images.mdx b/...itoring/aws-lambda-monitoring/enable-lambda-monitoring/containerized-images.mdx
@@ -22,10 +22,10 @@ New Relic offers pre-built images that include our layer's different runtimes: J
 
  <Tabs>
         <TabsBar>
-                <TabsBarItem id="1">Dockerfile for Java</TabsBarItem>
-                <TabsBarItem id="2">Dockerfile for Node.js</TabsBarItem>
-                <TabsBarItem id="3">Dockerfile for Python</TabsBarItem>
-                <TabsBarItem id="4">Dockerfile for Extension-only</TabsBarItem>
+                <TabsBarItem id="java">Java</TabsBarItem>
+                <TabsBarItem id="node.js">Node.js</TabsBarItem>
+                <TabsBarItem id="python">Python</TabsBarItem>
+                <TabsBarItem id="extension"> Extension-only</TabsBarItem>
         </TabsBar>
 
         <TabsPages>

diff --git a/...onitoring/aws-lambda-monitoring/enable-lambda-monitoring/instrument-example.mdx b/...onitoring/aws-lambda-monitoring/enable-lambda-monitoring/instrument-example.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Step 3: Instrument a test Lambda function"
+title: "Instrument a test Lambda function"
 metaDescription: Step 3 of enabling New Relic's AWS Lambda monitoring.
 freshnessValidatedDate: never
 ---

diff --git a/...nitoring/aws-lambda-monitoring/enable-lambda-monitoring/instrument-your-own.mdx b/...nitoring/aws-lambda-monitoring/enable-lambda-monitoring/instrument-your-own.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Step 4: Instrument your own Lambda functions"
+title: "Instrument your own Lambda functions"
 metaDescription: Step 4 of enabling New Relic AWS Lambda monitoring.
 freshnessValidatedDate: never
 ---

diff --git a/...oring/aws-lambda-monitoring/enable-lambda-monitoring/set-up-cloudwatch-logs.mdx b/...oring/aws-lambda-monitoring/enable-lambda-monitoring/set-up-cloudwatch-logs.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Step 2: Set up AWS API Polling or Metric Streams"
+title: "Set up AWS API Polling or Metric Streams"
 metaDescription: Make sure AWS API Polling or Metric Streams is installed before you enable New Relic's AWS Lambda monitoring.
 freshnessValidatedDate: never
 ---