fix readme

Signed-off-by: Carlos Santana <[email protected]>

patterns/gitops/getting-started-argocd/README.md

@@ -109,12 +109,6 @@ Wait until all the ArgoCD applications' `HEALTH STATUS` is `Healthy`. Use Crl+C
 watch kubectl get applications -n argocd
 ```
 
-## Access ArgoCD
-Access ArgoCD's UI, run the command from the output:
-```shell
-terraform output -raw access_argocd
-```
-
 ### Verify the Addons
 Verify that the addons are ready:
 ```shell
@@ -123,7 +117,11 @@ kubectl get deployment -n kube-system \
   metrics-server
 ```
 
-
+## Access ArgoCD
+Access ArgoCD's UI, run the command from the output:
+```shell
+terraform output -raw access_argocd
+```
 
 ## Deploy the Workloads
 Deploy a sample application located in [k8s/game-2048.yaml](k8s/game-2048.yaml) using ArgoCD:
@@ -148,18 +146,18 @@ Wait until the Ingress/game-2048 `MESSAGE` column value is `Successfully reconci
 kubectl events -n game-2048 --for ingress/game-2048 --watch
 ```
 
-
-
 ### Access the Application using AWS Load Balancer
-Retrieve the ingress URL for the application:
+Verify the application endpoint health using `curl`:
 ```shell
-echo "Application URL: http://$(kubectl get -n game-2048 ingress game-2048 -o jsonpath='{.status.loadBalancer.ingress[0].hostname}')"
+curl -I $(kubectl get -n game-2048 ingress game-2048 -o jsonpath='{.status.loadBalancer.ingress[0].hostname}')
 ```
-Verify the application enpoint health using `curl`:
+The first line of the output should be `HTTP/1.1 200 OK`.
+
+Retrieve the ingress URL for the application:
 ```shell
-curl -I $(kubectl get -n game-2048 ingress game-2048 -o jsonpath='{.status.loadBalancer.ingress[0].hostname}')
+echo "Application URL: http://$(kubectl get -n game-2048 ingress game-2048 -o jsonpath='{.status.loadBalancer.ingress[0].hostname}')"
 ```
-The first line of the output should have `HTTP/1.1 200 OK`.
+
 
 ### Container Metrics
 Check the application's CPU and memory metrics: