diff --git a/patterns/vpc-lattice/cross-cluster-pod-communication/README.md b/patterns/vpc-lattice/cross-cluster-pod-communication/README.md
index f5c037dafb..fda0a1f07d 100644
--- a/patterns/vpc-lattice/cross-cluster-pod-communication/README.md
+++ b/patterns/vpc-lattice/cross-cluster-pod-communication/README.md
@@ -7,7 +7,7 @@ This pattern showcases secure multi-cluster communication between two EKS cluste
 
 With this solution we showcase how to configure Amazon VPC Lattice using the AWS Gateway API Controller in order to manage Amazon VPC Lattice resources through native Kubernetes Gateway API objects. This pattern deploys two distinct VPCs each having it's own EKS cluster, which contain an application that will be used to demonstrate cross-cluster communication.
 
-The cross-cluster communication will be established through Amazon VPC Lattice, using a private Amazon Route53 domain name protected by a TLS Certificate issued by Certificate Managed and supported by an AWS Private Certificate Authority.
+The cross-cluster communication will be established through Amazon VPC Lattice, using a private Amazon Route53 domain name protected by a TLS Certificate issued by Certificate Manager (ACM) and supported by an AWS Private Certificate Authority.
 
 ![vpc-lattice-pattern-environment.png](https://raw.githubusercontent.com/aws-ia/terraform-aws-eks-blueprints/main/patterns/vpc-lattice/cross-cluster-pod-communication/assets/vpc-lattice-pattern-cross-cluster.png)