Skip to content

Commit f3a812e

Browse files
filippomcCopilot
andauthored
Apply suggestions from code review
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
1 parent c7ee1bb commit f3a812e

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

infrastructure/cluster-configuration/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ helm repo update
2222
helm install ingress-nginx ingress-nginx/ingress-nginx
2323
```
2424

25-
On localclusters and GCP/GKE, the nginx-ingress chart will deploy a Load Balancer with a given IP address, while . Use that address to create the CNames and A records for the website.
25+
On localclusters and GCP/GKE, the nginx-ingress chart will deploy a Load Balancer with a given IP address, while in other environments, you may need to configure the Load Balancer manually. Use that address to create the CNames and A records for the website.
2626

2727

2828

infrastructure/cluster-configuration/aws-setup.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -90,7 +90,7 @@ the following CNAME entries are needed
9090
- *.myapp [LB_ADDRESS]
9191

9292

93-
The easiest way to get the load balancer addressis to do the deployment and
93+
The easiest way to get the load balancer address is to do the deployment and
9494
from the ingress with
9595

9696
```

0 commit comments

Comments
 (0)