diff --git a/patterns/vpc-lattice/README.md b/patterns/vpc-lattice/README.md
index ed0c46eb0c..58ed00c581 100644
--- a/patterns/vpc-lattice/README.md
+++ b/patterns/vpc-lattice/README.md
@@ -7,7 +7,7 @@ This pattern demonstrates how to expose an EKS cluster hosted application to an
 
 ## Scenario
 
-With this soluton we showcase how to configure Amazon VPC Lattice using the AWS Gateway API Controller in order to manage Amazon VPC Lattice resources through native K8S Gateway API objects. This pattern deploys two distinct VPCs with a client application running in one of them and a server application in the other. The server application is deployed inside an EKS cluster and made exposed to the client application through Amazon VPC Lattice which establishes connectivity between the two applications. Further we demonstrate how to configure a custom domain name for the exposed service using Amazon Route53.
+With this soluton we showcase how to configure Amazon VPC Lattice using the AWS Gateway API Controller in order to manage Amazon VPC Lattice resources through native K8S Gateway API objects. This pattern deploys two distinct VPCs with a client application running in one of them and a server application in the other. The server application is deployed inside an EKS cluster and made exposed to the client application through Amazon VPC Lattice which establishes connectivity between the two applications. Further we demonstrate how to configure a custom domain name for the exposed service using Amazon Route53 and the external-dns project.
 
 ![diagram](assets/diagram.png)
 
diff --git a/patterns/vpc-lattice/assets/diagram.png b/patterns/vpc-lattice/assets/diagram.png
index 1c74adbfe5..6cea6fd489 100644
Binary files a/patterns/vpc-lattice/assets/diagram.png and b/patterns/vpc-lattice/assets/diagram.png differ