diff --git a/08-NEW-ELB-Application-LoadBalancers/08-03-ALB-Ingress-ContextPath-Based-Routing/README.md b/08-NEW-ELB-Application-LoadBalancers/08-03-ALB-Ingress-ContextPath-Based-Routing/README.md
index 82fc2e48..b9ac01d6 100755
--- a/08-NEW-ELB-Application-LoadBalancers/08-03-ALB-Ingress-ContextPath-Based-Routing/README.md
+++ b/08-NEW-ELB-Application-LoadBalancers/08-03-ALB-Ingress-ContextPath-Based-Routing/README.md
@@ -7,7 +7,7 @@ description: Learn AWS Load Balancer Controller - Ingress Context Path Based Rou
 - Discuss about the Architecture we are going to build as part of this Section
 - We are going to deploy all these 3 apps in kubernetes with context path based routing enabled in Ingress Controller
   - /app1/* - should go to app1-nginx-nodeport-service
-  - /app2/* - should go to app1-nginx-nodeport-service
+  - /app2/* - should go to app2-nginx-nodeport-service
   - /*    - should go to  app3-nginx-nodeport-service
 - As part of this process, this respective annotation `alb.ingress.kubernetes.io/healthcheck-path:` will be moved to respective application NodePort Service. 
 - Only generic settings will be present in Ingress manifest annotations area `04-ALB-Ingress-ContextPath-Based-Routing.yml`