Update README.md

README.md

@@ -27,9 +27,9 @@ At a high level, we will be following the steps outlined below for this solution
 
 Requires an ECS cluster. For deploying the Prometheus Node Exporter, a cluster with EC2 instances is required. All deployment artifacts are under the [deploy](https://github.com/aws-samples/prometheus-for-ecs/tree/main/deploy) directory. The deployment comprises the following components:
 - An ECS task comprising the Prometheus server, AWS Sig4 proxy and the service discovery application containers
-- 
+
 - A mock web application that is instrumented with Prometheus client library and exposes an HTTP endpoint */work*. The application has an internal load generator that sends client requests to the HTTP endpoint. The service exposes a [Counter](https://prometheus.io/docs/concepts/metric_types/#counter) named *http_requests_total* and a [Histogram](https://prometheus.io/docs/concepts/metric_types/#histogram) named *request_durtaion_milliseconds*
-- 
+
 - Prometheus Node Exporter to monitor system metrics from every container instance in the cluster. This service is deployed using [*host* networking mode](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html#network_mode) and with the daemon scheduling strategy. Note that we can’t deploy the Node Exporter on AWS Fargate because it does not support the daemon scheduling strategy.