Merge pull request #3738 from newrelic/Fixing-AWS-Lambda-legacy-doc

Fixes some front matter weirdness in lambda doc
newrelic · Sep 1, 2021 · 4bd3e94 · 4bd3e94
2 parents 622acf2 + 60ee019
commit 4bd3e94
Show file tree

Hide file tree

Showing 2 changed files with 296 additions and 29 deletions.
diff --git a/...ing/enable-lambda-monitoring/enable-serverless-monitoring-aws-lambda-legacy.mdx b/...ing/enable-lambda-monitoring/enable-serverless-monitoring-aws-lambda-legacy.mdx
@@ -11,7 +11,7 @@ redirects:
   - /docs/understand-dependencies/distributed-tracing/enable-configure/aws-lambda
 ---
 
-On this page, you will learn how to manually instrument your lambda function. It is organized by runtime language.
+On this page, you will learn how to manually instrument your lambda function. It's organized by runtime language.
 
 <CollapserGroup>
   <Collapser
@@ -453,4 +453,4 @@ newrelic.agent.record_custom_event('CustomEvent', {'foo': 'bar'})
   The New Relic decorator gathers data about the Lambda execution, generates a JSON message, and logs it to CloudWatch Logs. Next, [configure CloudWatch to send those logs to New Relic](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/instrument-your-own/#manual-stream-logs).
 </Collapser>
 </CollapserGroup>
-```
+