Update src/content/docs/infrastructure/elastic-container-service-inte…

…gration/installation/install-ecs-integration.mdx

Co-authored-by: Guillermo Sanchez Gavier <gsanchez@newrelic.com>

src/content/docs/infrastructure/elastic-container-service-integration/installation/install-ecs-integration.mdx

@@ -16,7 +16,7 @@ New Relic's ECS integration reports and displays performance data from your [Ama
 
 Before you install our ECS integration, we recommend reviewing the [requirements](/docs/introduction-amazon-ecs-integration#requirements). During the install process:
 
-* **For EC2 and ECS Anywhere launch type:** The infrastructure agent (`newrelic-infra`) gets deployed onto an ECS cluster as a service using the [daemon scheduling](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/scheduling_tasks.html) strategy. This deployment installs the infrastructure agent in all the container instances of the cluster. The infrastructure agent then monitors ECS and Docker containers.
+* **For EC2 and External (ECS Anywhere) launch type:** The infrastructure agent (`newrelic-infra`) gets deployed onto an ECS cluster as a service using the [daemon scheduling](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/scheduling_tasks.html) strategy. This deployment installs the infrastructure agent in all the container instances of the cluster. The infrastructure agent then monitors ECS and Docker containers.
 
 * **For AWS Fargate launch type:** The infrastructure agent (`newrelic-infra`) gets deployed as a sidecar in every task to monitor. The [Amazon AWS Fargate documentation](https://aws.amazon.com/blogs/compute/nginx-reverse-proxy-sidecar-container-on-amazon-ecs/) defines a sidecar as a way to move part of a service's core responsibility into a containerized module that is deployed alongside the core application.