Updated README.md

lab/us-gov-east-1/vpc/cluster/eks-prometheus/README.md

@@ -28,11 +28,11 @@ This module is dependent on EKS module (eks). The cluster should exist already f
     prometheus_server_internal_endpoint
 
 ### Issues observed/fixed
-    1. The rwo_storage_class value had to be updated from "gp3" to "gp3-encrypted"
-    2. The node_exporter_tag value had to be updated from "1.6.1" to "v1.8.1"
-    3. The kube_state_metrics_tag value had to be updated from "2.10.0" to "v2.6.0"
-    4. The alertmanager_tag value had to be updated from
-    5. The helm chart set config for the ecr image had to be split into 2 components, one for registry and other for repository as an example mentioned below:
+1. The rwo_storage_class value had to be updated from "gp3" to "gp3-encrypted"
+2. The node_exporter_tag value had to be updated from "1.6.1" to "v1.8.1"
+3. The kube_state_metrics_tag value had to be updated from "2.10.0" to "v2.6.0"
+4. The alertmanager_tag value had to be updated from
+5. The helm chart set config for the ecr image had to be split into 2 components, one for registry and other for repository as an example mentioned below:
     ```
     set {
     name = "kube-state-metrics.image.registry"
@@ -43,7 +43,7 @@ This module is dependent on EKS module (eks). The cluster should exist already f
     value = module.images.images[local.ksm_key].dest_repository
   }
   ```
-  6. In some other cases the image ecr repository had to be split by the colon separatory (:)
+6. In some other cases the image ecr repository had to be split by the colon separatory (:)
     ```
     set {
     name = "alertmanager.configmapReload.image.repository"