diff --git a/packages/aws-cdk-lib/aws-lambda/lib/event-source-mapping.ts b/packages/aws-cdk-lib/aws-lambda/lib/event-source-mapping.ts
index 43548757380ea..1f49011ca1bd5 100644
--- a/packages/aws-cdk-lib/aws-lambda/lib/event-source-mapping.ts
+++ b/packages/aws-cdk-lib/aws-lambda/lib/event-source-mapping.ts
@@ -292,8 +292,15 @@ export interface IEventSourceMapping extends cdk.IResource {
  * Usually, you won't need to define the mapping yourself. This will usually be done by
  * event sources. For example, to add an SQS event source to a function:
  *
- *    import { SqsEventSource } from 'aws-cdk-lib/aws-lambda-event-sources';
- *    lambda.addEventSource(new SqsEventSource(sqs));
+ * ```ts
+ * import * as sqs from 'aws-cdk-lib/aws-sqs';
+ * import * as eventsources from 'aws-cdk-lib/aws-lambda-event-sources';
+ *
+ * declare const handler: lambda.Function;
+ * declare const queue: sqs.Queue;
+ *
+ * handler.addEventSource(new eventsources.SqsEventSource(queue));
+ * ```
  *
  * The `SqsEventSource` class will automatically create the mapping, and will also
  * modify the Lambda's execution role so it can consume messages from the queue.