From d07bb81069cecea01374434da812cd7336ee1894 Mon Sep 17 00:00:00 2001
From: apgordon312 <ashleypgordon1@gmail.com>
Date: Sun, 4 May 2025 10:59:47 -0700
Subject: [PATCH] Update ingress-controller-elastic-kubernetes-services.md

Removed gerunds from headings.
---
 ...ingress-controller-elastic-kubernetes-services.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/content/nginx/deployment-guides/amazon-web-services/ingress-controller-elastic-kubernetes-services.md b/content/nginx/deployment-guides/amazon-web-services/ingress-controller-elastic-kubernetes-services.md
index f97817abe..3a66f745d 100644
--- a/content/nginx/deployment-guides/amazon-web-services/ingress-controller-elastic-kubernetes-services.md
+++ b/content/nginx/deployment-guides/amazon-web-services/ingress-controller-elastic-kubernetes-services.md
@@ -33,7 +33,7 @@ The `PREFIX` argument specifies the repo name in your private container registry
    
 
 <span id="amazon-eks"></span>
-## Creating an Amazon EKS Cluster
+## Create an Amazon EKS Cluster
 You can create an Amazon EKS cluster with:
 - the AWS Management Console
 - the AWS CLI
@@ -46,7 +46,7 @@ This guide covers the `eksctl` command as it is the simplest option.
 2. Create an Amazon EKS cluster by following the instructions in the [AWS documentation](https://docs.aws.amazon.com/eks/latest/userguide/getting-started-eksctl.html). Select the <span style="white-space: nowrap; font-weight:bold;">Managed nodes – Linux</span> option for each step. Note that the <span style="white-space: nowrap;">`eksctl create cluster`</span> command in the first step can take ten minutes or more.
 
 <span id="amazon-ecr"></span>
-## Pushing the NGINX Plus Ingress Controller Image to AWS ECR
+## Push the NGINX Plus Ingress Controller Image to AWS ECR
 
 This step is only required if you do not plan to use the prebuilt NGINX Open Source image.
 
@@ -81,7 +81,7 @@ This step is only required if you do not plan to use the prebuilt NGINX Open Sou
    ```
 
 <span id="ingress-controller"></span>
-## Installing the NGINX Plus Ingress Controller
+## Install the NGINX Plus Ingress Controller
 
 Use [our documentation](https://docs.nginx.com/nginx-ingress-controller/installation/installation-with-manifests/) to install the NGINX Plus Ingress Controller in your Amazon EKS cluster.
 
@@ -97,7 +97,7 @@ You need a Kubernetes `LoadBalancer` service to route traffic to the NGINX Ingre
 
 We also recommend enabling the PROXY Protocol for both the NGINX Plus Ingress Controller and your NLB target groups. This is used to forward client connection information. If you choose not to enable the PROXY protocol, see the [Appendix](#appendix).
 
-### Configuring a `LoadBalancer` Service to Use NLB
+### Configure a `LoadBalancer` Service to Use NLB
 
 Apply the manifest `deployments/service/loadbalancer-aws-elb.yaml` to create a `LoadBalancer` of type NLB:
 
@@ -105,7 +105,7 @@ Apply the manifest `deployments/service/loadbalancer-aws-elb.yaml` to create a `
    kubectl apply -f deployments/service/loadbalancer-aws-elb.yaml
    ```
 
-### Enabling the PROXY Protocol
+### Enable the PROXY Protocol
 
 1. Add the following keys to the `deployments/common/nginx-config.yaml` config map file:
 
@@ -158,7 +158,7 @@ Apply the manifest `deployments/service/loadbalancer-aws-elb.yaml` to create a `
 
 
 <span id="appendix"></span>
-## Appendix: Disabling the PROXY Protocol
+## Appendix: Disable the PROXY Protocol
 
 If you want to disable the PROXY Protocol, perform these steps.